|
1.
|
Clear description of the referenced document:
|
|
|
|
Name:
|
IETF RFC 4703 (2006)
|
|
Title:
|
Resolution of Fully Qualified Domain Name (FQDN) Conflicts among Dynamic Host Configuration Protocol (DHCP) Clients
|
|
|
2.
|
Status of approval:
|
|
|
Standards track document - Proposed standard approved in 2006.
|
|
3.
|
Justification for the specific reference:
|
|
|
FQDN used in the CSRs is defined by this RFC
|
|
4.
|
Current information, if any, about IPR issues:
|
|
|
Information on IPR issues regarding RFCs is available at: https://datatracker.ietf.org/ipr/search/. Specifically: https://datatracker.ietf.org/ipr/search/?draft=&rfc=8446&submit=rfc&doctitle=&group=&holder=&iprtitle=&patent=
|
|
5.
|
Other useful information describing the "Quality" of the document:
|
|
|
RFC 4703 is a Proposed Standard. This document has been reviewed extensively in IETF and widely used in real world.
|
|
6.
|
The degree of stability or maturity of the document:
|
|
|
RFC is a standards-track document and is currently in the "Proposed Standard" state.
|
|
7.
|
Relationship with other existing or emerging documents:
|
|
|
|
|
8.
|
Any explicit references within that referenced document should also be listed:
|
|
|
Normative References/
[1] Bradner, S., "Key words for use in RFCs to Indicate Requirement/
Levels", BCP 14, RFC 2119, March 1997./
/
[2] Stapp, M., Lemon, T., and A. Gustafsson, "A DNS Resource Record/
(RR) for Encoding Dynamic Host Configuration Protocol (DHCP)/
Information (DHCID RR), RFC 4701, October 2006./
/
[3] Vixie, P., Thomson, S., Rekhter, Y., and J. Bound, "Dynamic/
Updates in the Domain Name System (DNS UPDATE)", RFC 2136,/
April 1997./
/
[4] Droms, R., "Dynamic Host Configuration Protocol", RFC 2131,/
March 1997./
/
[5] Droms, R., Bound, J., Volz, B., Lemon, T., Perkins, C., and M./
Carney, "Dynamic Host Configuration Protocol for IPv6 (DHCPv6)",/
RFC 3315, July 2003./
/
Informative References:/
[6] Mockapetris, P., "Domain names - implementation and/
specification", STD 13, RFC 1035, November 1987./
/
[7] Malkin, G., "Internet Users' Glossary", FYI 18, RFC 1983,/
August 1996./
/
[8] Stapp, M., Volz, B., and Y. Rekhter, "The Dynamic Host/
Configuration Protocol (DHCP) Client Fully Qualified Domain/
Name (FQDN) Option", RFC 4702, October 2006./
[9] Volz, B., "The Dynamic Host Configuration Protocol for IPv6/
(DHCPv6) Client Fully Qualified Domain Name (FQDN) Option", RFC/
4704, October 2006./
/
[10] Wellington, B., "Secure Domain Name System (DNS) Dynamic/
Update", RFC 3007, November 2000./
/
[11] Lemon, T. and B. Sommerfeld, "Node-specific Client Identifiers/
for Dynamic Host Configuration Protocol Version Four (DHCPv4)",/
RFC 4361, February 2006./
/
[12] Alexander, S. and R. Droms, "DHCP Options and BOOTP Vendor/
Extensions", RFC 2132, March 1997./
/
[13] Vixie, P., Gudmundsson, O., Eastlake, D., and B. Wellington,/
"Secret Key Transaction Authentication for DNS (TSIG)",/
RFC 2845, May 2000./
/
[14] Droms, R. and W. Arbaugh, "Authentication for DHCP Messages",/
RFC 3118, June 2001./
|
|
9.
|
Qualification of
ISOC/IETF:
|
|
|
9.1-9.6 Decisions of ITU Council to admit ISOC to participate in the work of the Sector (June 1995 and June 1996).
9.7 The Internet Engineering Steering Group (IESG) is responsible for ongoing maintenance of the RFCs when the need arises. Comments on RFCs and corresponding changes are accommodated through the existing standardization process.
9.8 Each revision of a given RFC has a different RFC number, so no confusion is possible. All RFCs always remain available on-line. An index of RFCs and their status may be found in the IETF archives at http://www.rfc-editor.org/rfc.html.
|
|
10.
|
Other (for any supplementary information):
|
|
|
None
|
|
